Increasing storage space for processes impacting data storage systems

ABSTRACT

A processing request is received. The processing request includes information about a first location where a set of data is stored and information about a second location where the set of data is to be transferred. The size of the set of data is determined. The size of the available portion of the second location is determined. If the size of the set of data is smaller than the size of the available portion of the second location is determined. Responsive to determining the size of the set of data is larger than the size of the available portion of the second location, the size of the available portion is requested to be increased. The size of the available portion of the second location is increased to a size larger than the determined size of the set of data.

BACKGROUND

The present invention relates generally to the field of data storage,and more particularly to increasing storage space for processes in datastorage systems.

In computer software, and particularly computer databases, the term“data warehouse” is generally used to refer to a unified data repositoryfor all customer-centric data. A data warehouse environment tends to bequite large and can store a significant amount of data. The data storedin the data warehouse can be cleaned, transformed, and catalogued. Thedata can be used by business professionals for performing businessrelated operations, such as data mining, online analytical processing,and decision support. Typically, a data warehouse is associated with anextract, transform, and load (ETL) processes and business intelligencetools. The ETL processes are capable of extracting data from sourcesystems and bringing the data into a data warehouse.

SUMMARY

Embodiments of the present invention include a method, computer programproduct, and system for managing data storage. In one embodiment, aprocessing request is received. The processing request includesinformation about a first location where a set of data is stored andinformation about a second location where the set of data is to betransferred. The size of the set of data is determined. The size of theavailable portion of the second location is determined. If the size ofthe set of data is smaller than the size of the available portion of thesecond location is determined. Responsive to determining the size of theset of data is larger than the size of the available portion of thesecond location, the size of the available portion is requested to beincreased. The size of the available portion of the second location isincreased to a size larger than the determined size of the set of data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a cloud computing node, in accordance with an embodimentof the present invention;

FIG. 2 depicts a cloud computing environment, in accordance with anembodiment of the present invention;

FIG. 3 depicts abstraction model layers, in accordance with anembodiment of the present invention;

FIG. 4 depicts a functional block diagram of a data processingenvironment, in accordance with an embodiment of the present invention;and

FIG. 5 depicts a flowchart of operational steps of a program formanaging data storage, in accordance with an embodiment of the presentinvention.

DETAILED DESCRIPTION

Embodiments of the present invention provide for managing data storagein a data processing environment. Embodiments of the present inventionprovide for receiving a processing request that includes the movement ofdata from one location to another. Embodiments of the present inventioncan provide for modifying the data before it is stored in the newlocation. Embodiments of the present invention determine the size of thelocation the data is to be stored and the size of the data to be stored.Embodiments of the present invention determine if the size of the datato be stored is less than the size of the location the data is to bestored. Embodiments of the present invention provide for, if the size ofthe data to be stored is larger than the size of the location the datais to be stored, requesting an increase in the size of the location thedata is to be stored. Embodiments of the present invention provide for,after the size of the location the data is to be stored is increased toa size larger than the size of the data to be stored, initiating theprocessing request.

Embodiments of the present invention recognize that programs do not knowthe amount of space available at the target location when processingdata. Embodiments of the present invention recognize that it would beadvantageous for a program to dynamically increase the space allocatedto the program for the process so as to have enough space to processdata. Embodiments of the present invention recognize that currently,programs abort their processing of data when the target system does nothave sufficient space to store the data being processed.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed. The present invention will now be described in detailwith reference to the Figures.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based e-mail).The consumer does not manage or control the underlying cloudinfrastructure including network, servers, operating systems, storage,or even individual application capabilities, with the possible exceptionof limited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting forload-balancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, a schematic of an example of a cloud computingnode is shown. Cloud computing node 10 is only one example of a suitablecloud computing node and is not intended to suggest any limitation as tothe scope of use or functionality of embodiments of the inventiondescribed herein. Regardless, cloud computing node 10 is capable ofbeing implemented and/or performing any of the functionality set forthhereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, hand-held or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system-executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 1, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnects (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, external disk drive arrays,RAID systems, tape drives, and data archival storage systems, etc.

Referring now to FIG. 2, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 comprises one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 2 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 3, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 2) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 3 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may comprise applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and data management 96.

FIG. 4 is a functional block diagram illustrating a data processingenvironment, generally designated 400, in accordance with one embodimentof the present invention. FIG. 4 provides only an illustration of oneimplementation and does not imply any limitations with regard to thesystems and environments in which different embodiments may beimplemented. Many modifications to the depicted embodiment may be madeby those skilled in the art without departing from the scope of theinvention as recited by the claims.

An embodiment of data processing environment 400 includes source device410, target device 420 and management device 430, interconnected overnetwork 402. Network 402 can be, for example, a local area network(LAN), a telecommunications network, a wide area network (WAN) such asthe Internet, or any combination of the three, and include wired,wireless, or fiber optic connections. In general, network 402 can be anycombination of connections and protocols that will supportcommunications between source device 410, target device 420, andmanagement device 430, and any other computer connected to network 402,in accordance with embodiments of the present invention.

In example embodiments, source device 410 can be a laptop, tablet, ornetbook personal computer (PC), a desktop computer, a personal digitalassistant (PDA), a smart phone, or any programmable electronic devicecapable of communicating with any computing device within dataprocessing environment 400. In certain embodiments, source device 410collectively represents a computer system utilizing clustered computersand components (e.g., database server computers, application servercomputers, etc.) that act as a single pool of seamless resources whenaccessed by elements of data processing environment 400, such as in acloud computing environment. In general, source device 410 isrepresentative of any electronic device or combination of electronicdevices capable of executing computer readable program instructions.Source device 410 can include components as depicted and described indetail with respect to cloud computing node 10, as described inreference to FIG. 1, in accordance with embodiments of the presentinvention. Target device 420 and management device 430 can besubstantially similar to source device 410 and have substantiallysimilar components. Source device 410, target device 420, and managementdevice 430 can be nodes that are part of cloud computing environment 50.

In an embodiment, source device 410 includes source location 412. Sourcelocation 412 is an organized collection of data. Data found in sourcelocation 412 is typically organized to model relevant aspects of realityin a way that supports processes requiring the information found insource location. Source location 412 can be implemented with any type ofstorage device capable of storing data that can be accessed and utilizedby source device 410, such as a database server, a hard disk drive, or aflash memory. In other embodiments, source location 412 can beimplemented with multiple storage devices within source device 410. Inan embodiment, source location 412 is the location of the source file(i.e. data) to be processed by management program 432.

Alternatively, source location 412 can be implemented with any computerreadable storage medium as found in the art. For example, the computerreadable storage medium can be a tangible device that can retain andstore instructions for use by an instruction execution device. Thecomputer readable storage medium can be, for example, but is not limitedto, an electronic storage device, a magnetic storage device, an opticalstorage device, an electromagnetic storage device, a semiconductorstorage device, or any suitable combination of the foregoing. Anon-exhaustive list of more specific examples of the computer readablestorage medium includes the following: a portable computer diskette, ahard disk, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or Flash memory), a staticrandom access memory (SRAM), a portable compact disc read-only memory(CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk,a mechanically encoded device such as punch-cards or raised structuresin a groove having instructions recorded thereon, and any suitablecombination of the foregoing.

In an embodiment, target device 420 includes target location 422. Targetlocation 422 is an organized collection of data. Data found in targetlocation 422 is typically organized to model relevant aspects of realityin a way that supports processes requiring the information found intarget location. Target location 422 can be implemented with any type ofstorage device capable of storing data that can be accessed and utilizedby target device 420, such as a database server, a hard disk drive, or aflash memory. In other embodiments, target location 422 can beimplemented with multiple storage devices within target device 420. Inan embodiment, target location 422 is the destination of source file(i.e., data), from source location 412, which is processed by managementprogram 432 or another program (not shown). In an alternativeembodiment, target location 422 can be located on the same device assource location 412.

Alternatively, target location 422 can be implemented with any computerreadable storage medium as found in the art. For example, the computerreadable storage medium can be a tangible device that can retain andstore instructions for use by an instruction execution device. Thecomputer readable storage medium can be, for example, but is not limitedto, an electronic storage device, a magnetic storage device, an opticalstorage device, an electromagnetic storage device, a semiconductorstorage device, or any suitable combination of the foregoing. Anon-exhaustive list of more specific examples of the computer readablestorage medium includes the following: a portable computer diskette, ahard disk, a random access memory (RAM), a read-only memory (ROM), anerasable programmable read-only memory (EPROM or Flash memory), a staticrandom access memory (SRAM), a portable compact disc read-only memory(CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk,a mechanically encoded device such as punch-cards or raised structuresin a groove having instructions recorded thereon, and any suitablecombination of the foregoing.

In one embodiment, management device 430 includes management program432. Management program 432 is a program, application, or subprogram ofa larger program that manages data storage in data processingenvironment 400. In an embodiment, management program 432 can managedata storage when data is transferred between source location 412 onsource device 410 and target location 422 on target device 420. In analternative embodiment, management program 432 can manage data storagewhen data is transferred between any computer(s) (not shown) that caninteract with network 402. In an embodiment, management program 432 canbe located anywhere that can interact computing devices accessible vianetwork 402 but manage data storage in any location accessible via thenetwork.

Management program 432 receives a request to process data from a sourcedevice 410 to a target device 420 via network 402. In an embodiment, theprocessing can be to a single file. In an alternative embodiment, theprocessing can occur to more than one file. In an embodiment, theprocessing request can be moving data from source location 412 to targetlocation 422. In an alternative embodiment, the processing request canbe moving data from source location 412 to target location 422 butmodifying the data before the data is stored at target location. Thedata can be modified on source device 410 before the data is transferredvia network 402, after the data has left source device and before thedata reaches target device 420 via another program (not shown)accessible via network, or on target device but before the data isstored to target location 422. The request includes the source file(i.e. data) and source location 412 of the source file and the targetlocation 422 of the file after processing. Management program 432determines the target location storage size and then determines theoutput size of the source file after processing. Management program 432determines if the output file size is smaller than the target location422 size, and if management program determines the output file size issmaller than the target location size, management program initiates theprocessing request. If management program 432 determines the output filesize is larger than the target location 422 size, management programrequests an increase in the target location size. In an embodiment, thetarget location 422 size can be increased via resources of cloudcomputing nodes 10, discussed previously. In an alternative embodiment,the target location 422 size can be increase via resources of targetdevice 420. Upon receiving an indication that the target location 422size has increased as requested, management program 432 initiates theprocessing request.

In any embodiment, management program 432 can include a user interface(not shown). A user interface is a program that provides an interfacebetween a user and an application. A user interface refers to theinformation (such as graphic, text, and sound) a program presents to auser and the control sequences the user employs to control the program.There are many types of user interfaces. In one embodiment, the userinterface can be a graphical user interface (GUI). A GUI is a type ofuser interface that allows users to interact with electronic devices,such as a keyboard and mouse, through graphical icons and visualindicators, such as secondary notations, as opposed to text-basedinterfaces, typed command labels, or text navigation. In computers, GUIswere introduced in reaction to the perceived steep learning curve ofcommand-line interfaces, which required commands to be typed on thekeyboard. The actions in GUIs are often performed through directmanipulation of the graphics elements. For example, client applicationcan be a web browser, a database program, etc.

FIG. 5 is a flowchart of workflow 500 depicting operational steps formanaging data storage in a data processing environment 400, inaccordance with an embodiment of the present invention. Workflow 500represents the operational steps to perform data management 96 inworkloads layer 90. In one embodiment, the steps of the workflow areperformed by management program 432. In an alternative embodiment, stepsof the workflow can be performed by any other program while working withmanagement program 432. In a preferred embodiment, a user, via a userinterface discussed previously, can invoke workflow 500 upon determiningthat they would like to process data from one location (i.e. sourcelocation 412) to another location (i.e. target location 422). In analternative embodiment, workflow 500 can be invoked automatically underthe control of another program, for example, upon a user of sourcedevice 410 indicating to a program (not shown) to move data from sourcelocation 412 to target location 422 and management program 432 can begina step in workflow 500.

Management program 432 receives a processing request (step 505). In anembodiment, management program 432 can be notified by a user via userinterface, discussed previously, of a processing request. In analternative embodiment, management program 432 can be notified of aprocessing request from another program (not shown). In an embodiment,the processing request can include the source file (i.e. data) to beprocessed, the source location 412 of the data, and the target location422 of the data. In an alternative embodiment, the processing requestcan also include information about transformation of the data that canoccur when the data is moved from source location 412 to target location422. For example, management program 432 can receive a processingrequest that is an Extract, Transform, Load (ETL) request. An ETLrequest includes an extraction of data from homogeneous or heterogeneousdata sources, transforming the data for storing in a proper format orstructure for querying and analysis purposes, and then loading thetransformed data into the final target. Management program 432 can workwith an ETL program (not shown) to complete the processing request. Inthe processing request, management program 432 receives informationabout the data including the source location 412 found on source device410 and the target location 422 found on target device 420. In analternative embodiment, target location 422 can be found on the samedevice that source location 412 is located on.

Management program 432 determines the target location size (step 510).In other words, management program determines the size of the datastorage available on the target location of the processing request. Inan embodiment, management program 432 can query target device 420 andrequest the size of target location 422. In an alternative embodiment,the size of target location 422 can be included in the processingrequest received in step 510. For example, management program 432queries a program (not shown) on target device 420, requesting the sizeof target location 422. Management program 432 receives an indicationthat the size of target location 422 is 1.475 gigabytes (GB).

Management program 432 determines the output file size (step 515). Inother words, management program 432 determines the size of the sourcefile, after processing occurs, that will be stored in target location422. In an embodiment, the source file is being moved from sourcelocation 412 to target location 422 and no modification to the sourcefile occur and the size of the source file in the source location is thesame as the size of the output file size in the target location. In analternative embodiment, the size of source file, stored in sourcelocation 412, can be different than the size of the output file, storedin target location 422. In an alternative embodiment, management program432 can determine the output file size with the help of another program(not shown). For example, when an ETL request occurs, the source file istransformed to the output file and the size of the files are different.Management program 432, in conjunction with ETL program (not shown),determines, the size of the source file is 1.352 GB and after thetransformation of the file, the size of the output file is 1.531 GB. Inan alternative example, multiple source files or systems can beprocessed. During processing, the fields of the source files can bedetermined and then a subset of the fields can be selected. Managementprogram 432 can determine the largest row size in the fields and thenmultiply that by the largest row size possible to determine the outputfile size. Additionally, supporting infrastructure can be required, suchas a database index, and the size of the supporting infrastructure isadded to the output file size.

Management program 432 determines if the output file size is smallerthan the target location size (decision block 520). In an embodiment,management program 432 determines if size of target location 422 islarge enough to store the output file based on the size of the outputfile. If management program 432 determines output file size is less thantarget location size (decision block 520, YES branch), managementprogram proceeds to step 535. For example, management program 432determines that the output file size (1.422 GB) is smaller than the sizeof the target location 422 (1.475 GB). In an alternative embodiment, ifthe output file size is equal to the target location size, managementprogram 432 proceeds to step 535.

If management program 432 determines the output file size is larger thanthe target location size (decision block 520, NO branch), managementprogram requests the target location size increase (step 525). Forexample, management program 432 determines that the output file size(1.532 GB) is larger than the size of the target location 422 (1.475GB). In an embodiment, management program 432 can increase the size oftarget location 422. In an alternative embodiment, management program432 can request another program (not shown), for example a program foundon target device 420, to increase the size of target location.Management program 432 can request for the size of target location 422to be any size equal to or larger than the size of the output file. Inan embodiment, management program 432 can request the storage devicesthat will be used to increase the size of target location 422. In analternative embodiment, management program 432 can request that anotherprogram determine the storage devices that will be used to increase thesize of target location. In an example, management program 432 canrequest for the size of target location 422 to increase using storagedevices (not shown) found on target device 420. In another example,management program 432 can request for the size of target location 422to increase using storage devices (not shown) not found on target device420 but accessible to target device via network 402. In yet anotherexample, management program 432 can request for the size of targetlocation 422 to increase via resources of cloud computing nodes 10,discussed previously.

Management program 432 receives an indication of target location sizeincrease (step 530). In an embodiment, management program 432 completesthe increase of the size of target location 422 and then monitor programcan proceed to step 535. In an alternative embodiment, managementprogram 432 receives an indication from another program (not shown) thatthe size of target location 422 has increased and management programthen can proceed to step 535. In an embodiment, the size of targetlocation 422 increases to a size equal to or larger than the size of theoutput file.

Management program 432 initiates processing request (step 535). In anembodiment, management program 432 initiates the processing request forsource file in source location 412 to move to target location 422. In analternative embodiment, management program 432, in conjunction withsource device 410 and target device 420, initiates the processingrequest for source file in source location 412 to move to targetlocation 422. In an alternative embodiment, management program 432 canindicate to another program (not shown), found on source device 410,target device 420, management device 430 or any other device (not shown)connected via network 402, to initiate the processing request.

The programs described herein are identified based upon the applicationfor which they are implemented in a specific embodiment of theinvention. However, it should be appreciated that any particular programnomenclature herein is used merely for convenience, and thus theinvention should not be limited to use solely in any specificapplication identified and/or implied by such nomenclature.

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the invention.The terminology used herein was chosen to best explain the principles ofthe embodiment, the practical application or technical improvement overtechnologies found in the marketplace, or to enable others of ordinaryskill in the art to understand the embodiments disclosed herein.

What is claimed is:
 1. A method for managing data storage, the methodcomprising the steps of: receiving, by one or more computer processors,a processing request, wherein the processing request includesinformation about a first location where a set of data is stored,information about a second location where the set of data is to betransferred, and the set of data being modified before moving the datato the second location, and wherein the process is an extract,transform, and load process, and wherein the set of data is one or morefiles; determining, by the one or more computer processors, a size ofthe set of data; determining, by the one or more computer processors, asize of an available portion of the second location; determining, by theone or more computer processors, if the size of the set of data issmaller than the size of the available portion of the second location;responsive to determining the size of the set of data is larger than thesize of the available portion of the second location, requesting, by theone or more computer processors, the size of the available portion ofthe second location be increased, wherein the size of the availableportion of the second location is increased to a size larger than thedetermined size of the set of data, and wherein the size of theavailable portion of the second location is increased using cloudresources; determining, by the one or more computer processors, the sizeof the modified set of data; determining, by the one or more computerprocessors, if the size of the modified set of data is smaller than thesize of the available portion of the second location; responsive todetermining the size of the modified set of data is larger than the sizeof the available portion of the second location, requesting, by the oneor more computer processors, the size of the available portion of thesecond location be increased, wherein the size of the available portionof the second location is increased to a size larger than the determinedsize of the modified set of data; and responsive to receiving anindication that the size of the available portion of the second locationhas increased, initiating, by the one or more computer processors, theprocessing request.